docs: align legacy positioning with project source#158
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the project name to "CompText V7" and refines the research positioning and API surface descriptions across several documentation files to emphasize deterministic replay integrity. Review feedback indicates that the name update is inconsistent, as several instances of the legacy name "Comptextv7" remain in "docs/API_SURFACE.md" and "docs/research_positioning.md", which should be corrected to align with the repository style guide.
| CompText V7 should treat API, dashboard, export, and report surfaces as | ||
| deterministic review and evidence handoff surfaces, not as runtime | ||
| orchestration, live monitoring, or platform expansion. Experiment outputs | ||
| should influence review decisions through lightweight Markdown, JSON, or CSV | ||
| summaries only. |
There was a problem hiding this comment.
While this paragraph is updated to use the canonical project name CompText V7, several other occurrences of the legacy name Comptextv7 remain in this file (e.g., on lines 5, 35, 80, and more). To fully align with the PR's goal of reducing confusion and adhere to the project's established naming convention, please consider updating all instances of the project name within this document for consistency.
References
- The repository style guide establishes 'CompText V7' as the canonical project name (lines 1, 4). For consistency, this name should be used throughout the project documentation. (link)
| # CompText V7 Research Positioning | ||
|
|
||
| CompTextv7 is a deterministic operational replay-validation and state-survivability prototype. It asks whether compact, replay-safe operational state can preserve the fixture-defined evidence, constraints, blockers, dependencies, recovery paths, and tool-order signals needed to review continuation after compression and reconstruction. The project is complementary to learned context-compression research, RAG evaluation, vector-memory systems, serving-layer cache optimization, and durable workflow infrastructure, but it does not replace those systems or claim solved AI memory. | ||
| CompText V7 is the deterministic replay-integrity layer for compressed operational agent traces. It asks whether compact or reconstructed operational state can preserve the evidence, constraints, blockers, dependencies, recovery paths, capability boundaries, and tool-order signals needed to replay a safe operational trajectory after compression. The project is complementary to learned context-compression research, RAG evaluation, vector-memory systems, serving-layer cache optimization, and durable workflow infrastructure, but it does not replace those systems or claim solved AI memory. |
There was a problem hiding this comment.
The heading and opening paragraph now correctly use CompText V7. However, the rest of the document still contains numerous instances of the legacy name Comptextv7 (e.g., on lines 5, 7, 23). This creates an inconsistent naming convention within the same file, which could be confusing for readers. To ensure consistency with the project's established naming, it would be beneficial to update all occurrences of the project name throughout this document.
References
- The repository style guide establishes 'CompText V7' as the canonical project name (lines 1, 4). For consistency, this name should be used throughout the project documentation. (link)
1 participant
Motivation
CompText V7in targeted legacy files to reduce confusion.Description
AGENTS.mdtitle to# CompText V7 Agent Instructionsand replace the first project-focus bullet with the canonical replay-integrity phrasing.docs/research_positioning.mdto the canonical replay-integrity language while preserving the rest of the document and its prototype-scoped caveats.docs/API_SURFACE.mdwith wording that treats API, dashboard, export, and report surfaces as deterministic review and evidence handoff surfaces (explicitly not runtime orchestration, live monitoring, or platform expansion).AGENTS.md,docs/research_positioning.md, anddocs/API_SURFACE.mdonly, with no changes to code, fixtures, artifacts, workflows, package files, README, or tests.Testing
npm run check, which invoked repository layout, TypeScript typechecks, validate/build steps, andpytestas part of the check pipeline, and completed without error.pytestreported283 passedand the overallnpm run checksucceeded.Codex Task